Skip to main content

What's New

Below are the changes made for each release.

Version 1.8 (April 2025)​

Changes

  • The following response code will be returned when the web service is unable to communicate with an internal EPS service.
Resource CodeResource Text
WEB-3000Internal Service Error

Version 1.7 (April 2022)​

Changes

New functionality is being introduced in the April 2022 release that will allow FI's to delete RDA Customers (Users) through the new RDAAdminWebservice. A new web service method was added, named DeleteCustomer, that can be used to delete a customer and its associated accounts.

The following element is required in the DeleteCustomerRequest:

  • HomeBankingID

Version 1.6 (July 2021)​

Changes

The Risk Profile options have now been expanded to include an additional Risk Setting for enabling the Minimum Amount Threshold through the RDAAdminWebService. This new feature will allow the FI to set a minimum amount threshold for deposits that will apply to all risk settings. If the transaction amount falls below this threshold, then the RDA deposit will not be evaluated for any other risk settings.

Minimum Amount Threshold - RDA deposited items that are below the minimum amount threshold will not be evaluated by any risk settings.

This new Risk Setting have been added to the below five (5) Risk Profile methods that will allow Integrators to take advantage of the new Risk Profile functionality. Integrators are not required to make any changes at this time unless they want to take advantage of this new Risk Profile option.

Version 1.5 (July 2019)​

Changes

  • New functionality is being introduced in the July 2019 release that will allow FI’s to delete RDA accounts through the new RDAAdminWebservice. In the UpdateAccountRequest method a new property will be added named “Deleted” with a description of “If this value is set to true the specified account will be deleted”. The default will be set to “False”. Integrators are not required to make any changes at this time unless they want to take advantage of this new functionality.

Version 1.4 (October 2018)​

The Risk Profile options have now been expanded to include an additional Risk Setting for managing Restrictive Endorsement Confidence Levels through the RDAAdminWebService. This new feature will allow the FI to control which confidence levels will automatically decline, approve, suspend and/or flag a deposit for review and can be enabled or disabled at any time.

Risk Setting 8: Restrictive Endorsement Confidence Levels

  • “Low” confidence level = A deposit with a restrictive endorsement confidence value below the Low setting will be “Declined” up-front and rejected back to the depositor. It will not be displayed in the portal.

  • “Mid” confidence level = A deposit with a restrictive endorsement confidence value between the Low and Mid settings will be treated as an exception with a “Suspend” action and will be displayed in the portal for FI review.

  • “High” confidence level = A deposit with a restrictive endorsement confidence value between the Mid and High settings will be “Approved” and display in the portal for FI review. A deposit with a restrictive endorsement confidence value above the "High" setting will be “Approved” up-front and will not be displayed in the portal.

This new Risk Setting and corresponding actions have been added to the below five (5) Risk Profile methods that will allow Integrators to take advantage of the new Risk Profile functionality. Integrators are not required to make any changes at this time unless they want to take advantage of the new Risk Profile options.

Version 1.3 (April 2018)​

The Risk Profile component that was added in the January 2018 release has now been expanded to include the additional two (2) Risk Settings which will allow Financial Institutions to:

Risk Setting 6: Twice the User’s Average Deposit and Above Amount

Approve or suspend a deposit submitted by a user that is twice their average deposit in the past 90 days and is above $X.XX dollars combined. The two new fields represent the “Above Amount” that should be specified for the risk setting and can be set to any value between $0.00 to $100,000.00. Along with the corresponding Risk Action which can be set to Disabled, Approve or Suspend.

Risk Setting 7 = Outside Normal Hours

Approve or suspend a deposit that is received outside normal deposit hours. The three new fields represent the “Begin” and “End” time for the "Normal Deposit Hours" that should be specified for the risk setting and can be set any value in the HH:MM AM/ PM format (Central time zone). Along with the corresponding Risk Action which can be set to Disabled, Approve or Suspend.

These new Risk Settings and Actions have been added to the below five (5) Risk Profile methods that will allow Integrators to take advantage of the new Risk Profile functionality.

Integrators are not required to make any changes at this time unless they want to take advantage of the new Risk Profile options.

Default Risk Profiles

EPS has also added the ability for FIs to now define default Risk Profiles from within the Partner Portal based on user type. The default options available for FIs to assign to Risk Profiles are “ConsumerCapture”, “MicroBusiness”, “None” and “Both” (ConsumerCapture and MicroBusiness). The ability to leverage these new defaults is now available when utilizing the RDA Admin WebService in the following way:

The AddCustomer method was updated to assign a default Risk Profile based on the CustomerType provided in the request.

  • If the CustomerType is Consumer, then a ConsumerCapture default Risk Profile is assigned
  • If a ConsumerCapture default doesn't exist, then a default of “Both” (ConsumerCapture and Microbusiness) Risk Profile is assigned
  • If the CustomerType is MicroBusiness, then a Microbusiness default Risk Profile is assigned
  • If a Micro Business default doesn't exist (None), then a default “Both” (ConsumerCapture and Microbusiness) Risk Profile is assigned

The UpdateRiskProfile method was updated in the DefaultOption property with the values of “ConsumerCapture”, “MicroBusiness”, “None” and “Both” (ConsumerCapture and MicroBusiness).

Version 1.2 (January 2018)​

JHA SmartMonitor – RDA’s New Risk Management Module

SmartMonitor is a new risk management module that dramatically expands RDA’s current velocity controls. It will allow Financial Institutions to review or suspend RDA deposits that violate one or more Financial Institution configured risk tests. SmartMonitor will make it much easier for Financial Institutions to determine when a deposit needs further examination.

Financial Institutions will administer SmartMonitor’s risk settings in a new component called a Risk Profile. Risk Profiles are being built on top of RDA’s current Velocity Templates, expanding their already powerful fraud mitigation power. In addition to velocity limits, Risk Profiles will include new “risk settings” that evaluate the legitimacy of the depositor and the deposit itself.

SmartMonitor will allow Financial Institutions to:

  • Suspend and review all RDA deposits made in the first few days, weeks or months after a user’s initial enrollment.
    • Risk Setting 1: Minimum Number of Days Enrolled
  • Suspend and review a set number of successful RDA deposits after a user’s initial enrollment.
    • Risk Setting 2: Minimum Number of Deposits since Enrollment
  • Suspend and review a user’s first deposit after the user has been dormant for a specified period of time.
    • Risk Setting 3: Zero Successful Deposits within the Last Number of Days
  • Suspend and review future RDA deposits (for a set number of days) after a user has a RDA deposit declined.
    • Risk Setting 4: Rejected Deposit in the Last Number of Days
  • Suspend and review future RDA deposits (for a set number of days) after a MICR Denylist violation. - Risk Setting 5: MICR Denylist Violation(s) in the Last Number of Days As part of SmartMonitor, EPS has added five (5) new Risk Profile methods that will allow Integrators to take advantage of the new Risk Profile functionality.

Integrators are not required to make any changes at this time unless they want to take advantage of the new Risk Profile options.

Below are the new Risk Profile methods as of the RDA January 2018 release:

Version 1.1 (October 2017)​

The following methods and elements need to be removed.

Version 1.0 (October 2016)​

The items listed below have been updated and will behave differently if you are converting from the old web service.

  • TokenCredentials will now be returned on each request to allow longer sessions. It is best to use the latest SecurityToken on each new request.
  • Each Request will now have a RequestId and RequestDate are now used for tracking. The RequestId is a correlation id field to allow the integrator to send a value that exists in their logs that would match our logs so that we can troubleshoot issues.
    • It would be best if the RequestId followed a simple format. That way the EPS support team can track multiple requests across the session as well as individual requests.
    • SessionId:RequestId
    • example call 1: 7523be8a-0dc5-41b1-aac1-201667f3d13e:e195f48e-f964-423a-adb8-f17c76c528aa
    • example call 2: 7523be8a-0dc5-41b1-aac1-201667f3d13e:72130a76-e9df-4a87-bfb2-c59a460062e9
  • Get RDC Transactions was split into two new methods.
    • GetItems
    • GetBatches